Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add isSandboxedPage #28

Merged
merged 1 commit into from
Jul 30, 2024
Merged

Add isSandboxedPage #28

merged 1 commit into from
Jul 30, 2024

Conversation

fregante
Copy link
Owner

Close #21

I need to double-check this.

@fregante fregante self-assigned this Jun 10, 2024
@fregante
Copy link
Owner Author

Judging by https://developer.chrome.com/docs/extensions/reference/manifest/sandbox, the logic is correct:

A sandboxed page won't have access to extension APIs, or direct access to non-sandboxed pages (it may communicate with them using postMessage()).

For example, here's how to specify that two extension pages are to be served in a sandbox [...]

  "sandbox": {
    "pages": [
      "page1.html",
      "directory/page2.html"
    ]
  },

@fregante fregante merged commit 5a6adef into main Jul 30, 2024
4 checks passed
@fregante fregante deleted the sandbox branch July 30, 2024 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Detect sandbox documents
1 participant